Okay, let's...

• Ensure that the PR description matches the style we're using for release PRs.
• Justify to ourselves if we should be issuing a minor point release or a media point release? Which one and why?
• Check if we have accidentally missed any behavioural changes from the CHANGELOG?

• Ensure that the PR description matches the style we're using for release PRs.

does this mean to simply copy changelog of this version as PR description?

Justify to ourselves if we should be issuing a minor point release or a media point release? Which one and why?

Not sure you are asking me or the maintainers, I have no opinion on this.

Can we assume that the current version of httpcore is the last one that we will be able to support in this release? Because httpcore changed the response.extensions type in encode/httpcore#762 I'm guessing we'll have type issues with the next httpcore release.

does this mean to simply copy changelog of this version as PR description?

Yep.

I have no opinion on this.

For the 0.x series we're using median point bumps for releases that include API changes. We've only got additions and fixes here, so we probably want a 0.24.2 release?

I'm guessing we'll have type issues with the next httpcore release.

I'm... not sure if the Mapping -> MutableMapping switch-up will cause a continuous integration issue or not.
It's not an issue in practise, because we're actually using dictionary instances throughout anyways. But it might cause a typing problem?

You could issue a draft PR where httpcore installs from the repo source if you wanted to double check.

• Shall we consider rolling an httpcore release prior to releasing this one for httpx?
• Should we resolve Change the type of Extensions from Mapping to MutableMapping. #2794 for this release?

For the 0.x series we're using median point bumps for releases that include API changes. We've only got additions and fixes here, so we probably want a 0.24.2 release?

I'll update the version number according your discussion and decision 🙂

I'm guessing we'll have type issues with the next httpcore release.

I'm... not sure if the Mapping -> MutableMapping switch-up will cause a continuous integration issue or not. It's not an issue in practise, because we're actually using dictionary instances throughout anyways. But it might cause a typing problem?

You could issue a draft PR where httpcore installs from the repo source if you wanted to double check.

• Shall we consider rolling an httpcore release prior to releasing this one for httpx?
• Should we resolve Change the type of Extensions from Mapping to MutableMapping. #2794 for this release?

I think if we want to include #2794, we should create a httpcore release (>=0.18.0) first, require master branch of httpcore is not a good idea.

I think if we want to include #2794, we should create a httpcore release (>=0.18.0) first

Indeed, yep.

I think the TODO list here looks like this(?)...

• Drop Python 3.7 from httpcore. Drop Python 3.7 support httpcore#727
• Resolve Ensure HTTP/2 connections are gracefully closed on async cancellation httpcore#757
• Issue httpcore 0.18.0 release. Version 0.18.0 httpcore#768
• Resolve Change the type of Extensions from Mapping to MutableMapping. #2794.
• Resolve Drop support for Python 3.7 #2813
• Issue httpx 0.25.0 release.

Drop Python 3.7 from httpcore/httpx.

This doesn't need to be in todo list I think, we can drop them later

@trim21 Could you please include #2813 into this release? I merged it to master today morning.

For the 0.x series we're using median point bumps for releases that include API changes. We've only got additions and fixes here, so we probably want a 0.24.2 release?

Now we removed python3.7 support, I think it's definitely 0.25.0 not 0.24.2

@tomchristie now todo list is empty